Confirm the Action: Install and Activate Concurrently

Use this window to confirm or cancel your request to install and activate the retrieved internal code changes for the selected Central Processor Complexes (CPCs).

Installing and activating the retrieved changes makes them operational.

At this point in the task, retrieved internal code changes are:

• All changes you retrieved from their source to the support elements of the CPCs. That is, all changes that are eligible for being installed.
• But limited to the type of changes you selected for the task on a previous window: concurrent changes only.

Task

Use this window to complete the following task. Select the task for examples with step-by-step instructions.

• Install and activate internal code changes to make them operational.

Internal code change process

The window displays a summary of the internal code change process recommended by IBM. Installing and activating internal code changes is the fourth step (step D) of the process. Review the process before continuing.

Important:

You should cancel your request to install and activate internal code changes if you did not perform the first, second, or third steps (steps A, B, or C) of the process upon receiving the new internal code changes. That is:

• If you have not yet performed a backup of critical data of the CPCs and their support elements.
• Or if you have not yet accepted all previously installed and activated internal code changes.
• Or if you have not yet retrieved the new internal code changes provided to you by IBM.

You should confirm your request to install and activate new internal code changes only after completing the recommended steps described above.

Mirroring support element data

Mirroring support element data copies it from a CPC's primary support element to its alternate support element. By regularly mirroring support element data, you help ensure the alternate support element will look and work the same as the primary support element, should you ever need to switch to using the alternate support element (due to a primary support element hardware failure, for example).

Ordinarily, support element data is mirrored automatically each day. But you can use the Alternate Support Element task to mirror support element data immediately, at any time and for any reason. For example, you may want to mirror support element data immediately after installing internal code changes on the primary support element, to ensure the alternate support element is at the same internal code level right away (otherwise, the alternate support element would remain at the previous internal code level until its daily, automatic mirroring occurred).

Concurrent internal code changes

Activating concurrent internal code changes does not require activating the CPCs on which the changes are installed. For this reason, activating the internal code changes is considered a concurrent operation. That is, it occurs while the CPCs and their operating systems continue to operate.

You can confirm your request to install and activate concurrent internal code changes without affecting the operating system activity of the selected CPCs.